Business Analyst Community & Resources | Modern Analyst

COTS Information System Detailed Requirements Template

adrian — Sun, 16 Jun 2024 23:43:00 GMT

This spreadsheet-based template is intended to support documenting detailed requirements (DTRs) discussed in the article “What Requirements Are Needed When Implementing a COTS Information System?"

A business analyst is normally expected to document requirements by describing what is needed, avoiding how a solution might satisfy them. But a selected COTS product is an existing solution. A domain-specific information system solution includes user interface (UI), data import, export, report, or automated function capabilities. Additionally, a COTS product’s selection may have been influenced in part by its inclusion of domain-independent capabilities such as configurable workflows or business rules.

A complete set of DTRs identifies which “Out-of-the-Box” (OOTB) capabilities are to be implemented as is, which need changing, which aren’t needed, and which unsupported capabilities need to be added.

The article "What Requirements Are Needed When Selecting a COTS Information System?” discusses capability-specific high-level requirements (HLRs). Those requirements are intended to be of the “What, not How” variety.

Requirements in Context – Tool Extension Meta-Model

adrian — Sat, 06 Mar 2021 23:44:00 GMT

The purpose of this spreadsheet is to present details of a meta-model that can and has been used to extend Requirements Management (RM) or Application Lifecycle Management (ALM) tools. The rationale for applying these extensions is discussed in the article: Tool Support for Managing Requirements [In Context]

Trips-R-You Case Study: Requirements for an Automated Function Example

adrian — Tue, 14 Apr 2020 02:52:00 GMT

The purpose of this spreadsheet is to present an example of detailed requirements for an Automated Function (AF). The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples.

Trips-R-You Case Study: Data Import Requirements Example

adrian — Mon, 10 Feb 2020 00:09:00 GMT

The purpose of this spreadsheet is to present an example of detailed requirements for a data import interface. The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples.

Trips-R-You Case Study: Data Export Requirements Example

adrian — Sun, 09 Feb 2020 23:59:00 GMT

The purpose of this spreadsheet is to present an example of detailed requirements for a data export interface. The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples.

Trips-R-You Case Study: User Interface Example

adrian — Mon, 02 Dec 2019 00:36:00 GMT

The purpose of this spreadsheet is to present an example of detailed specifications for a screen-based user interface. The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples.

The following case study example high-level requirements identify the need for this user interface:

Trips-R-You Case Study: Report Example

adrian — Mon, 02 Dec 2019 00:23:00 GMT

The purpose of this spreadsheet is to present an example of detailed specifications for a report. The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples.

The following case study example high-level requirements identify the need for this report:

Trips-R-You Case Study: Requirements

adrian — Sun, 29 Sep 2019 20:04:00 GMT

The purpose of this spreadsheet is present an integrated, end-to-end set of requirement statement examples, based on the Trips-R-You Case Study. In IIBA® BABOK® V3 terminology, end-to-end means from Business Requirements to Stakeholder Requirements to Solution and Transition Requirements. The case study, and associated artifacts, use the more traditional business terms Goals, High-level Requirements (HLRs), and Detailed Requirements.

Trips-R-You Case Study: Data Dictionary

adrian — Sun, 29 Sep 2019 19:26:00 GMT

Section 3 begins by presenting one additional tool - a Data Dictionary. As the detail for a given HLR is discussed, the data-specific business needs involved are captured using this tool. The idea is to add entries about record types and fields (i.e. entities and attributes) the first time their need is discussed (e.g. an HLR for a specific screen or report). Once captured, those data-specific details are available for reference when those needs come up again, as they will, during discussions involving other HLRs. The detail in the data dictionary is shown to support a transition requirement for a new or updated database schema.

Product Backlog Template

sumit.soni — Mon, 18 Apr 2016 04:46:00 GMT

I have created Product Backlog Template, which is attached here. As, i am new to Agile, i want you guyz to go through it and let me know what additions/changes i should do in it.

Features include: Product Backlog, Sprints Backlog, Product Burndown Chart, User Stories

CBAP Skills Self-Assessment - BABOK v2.0

AlWilkinson — Mon, 15 Jun 2009 20:34:00 GMT

UPDATED for the BABOK Guide 2.0 !

This familiar checklist uses a Likert scale, and the Knowledge Areas of the BABOK Guide 2.0, to capture a personal estimation of readiness for the CBAP certification exam.

In a summary form, it provides a high-level review of the breadth of knowledge required of certification candidates. With this understanding they can chart an effective course of study, and gain confidence in their readiness as they prepare for the IIBA's professional certification.

CBAP Skills Self-Assessment - BABOK v1.6

AlWilkinson — Mon, 19 Jan 2009 09:57:00 GMT

Look yourself in the mirror. Get prepared. Take the plunge.

This checklist will help you keep track of your sense of readiness for the CBAP exam.

Use Case Points - Excel Template and Tutorial for Project Estimation

sehlhorst — Mon, 25 Aug 2008 12:35:00 GMT

Estimating the amount of work required to deliver software is hard. Estimating the amount of work in the very early stages of a project is even harder. A method was developed to estimate the amount of work required by analyzing what the system will allow its users to do. That method is called Estimating With Use Case Points.

Requirements and Test Cases Traceability Matrix

vneytcheva — Wed, 16 Jul 2008 17:40:00 GMT

This MS Excel traceability matrix could be used when a software tool is not available. It lists the business requirements and the functional requirements on a project related to them.

Requirements Traceability Matrix

vneytcheva — Wed, 16 Jul 2008 17:30:00 GMT

This MS Excel traceability matrix could be used when a software tool is not available. It provides a cross match between the business and functional requirements on a project.

Volere Stakeholder Analysis Template

adrian — Tue, 17 Jun 2008 04:55:00 GMT

This template helps you to identify the stakeholder roles, the representative(s) of each role and the type(s) of knowledge that you need from them for your given project.